-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
modify bug for template script to generate VC 2013 #21
base: master
Are you sure you want to change the base?
Conversation
Hi Luke, Thank you for providing this pull request. Can you provide a description of the script you were trying to migrate, and the problems you encountered? Also can you share your default.features file(s), from %ACE_ROOT%/bin/MakeProjectCreator/config/default.features. Also, can you share any custom configuration not generated by MPC. (Ideally this last bit should be empty. Best regards, |
Hi Phil, From: Phil Mesnier |
Hi Phil, Following is my sample script,it work fine under VC 2005 and 2008, but failed under 2013 ;project(LmxLibUtilToolsus):build_files{
}
from :
<%if(type_is_static)%>
<%if(exename || sharedname || staticname)%> to: <%if(type_is_static && staticname)%>
<%foreach(libpaths)%><%libpath%>;<%endfor%>%(AdditionalLibraryDirectories) 3.the following change is for consist with vc2008 <%if(!managed && debug_format)%> to: <%if(!managed && debug_format)%> with these change, both vc2008 and vc 2013 can use the same script and works well, I think this is the purpose of MPC development From: Phil Mesnier |
Hi Luke, Thank you for the updates. Now it is my turn to apologize for letting this linger. I think when I asked for any configuration changes, I was looking for changes to existing content, or new content that was required by the template changes you added. It seems all the config/luke*mpb files you've added are extensions you find personally useful, but are not required for others to benefit from your VC2013 template. Is this an accurate description of those files? I do not like that you prefix the mpb file names with "luke." I appreciate the motivation, but I think the base module name should be more product specific, or name specialization should be more product-specific. It might be better to collect your files into a separate directory and add documentation to indicate that you have assembled a list of useful projects that augment the new VC2013 template. In fact, are your new luke*mpb files specific to the new template, or are they useful for other MSVC's as well? I would like to discuss this with some folks back here, but I think adding a new "contrib" directory under which you could add a "luke" directory might do the trick. The new documentation will then state that to use these new base projects, one needs to add "$MPC_ROOT/contrib/luke/config/" to the "includes = " line of their local MPC.cfg file. In addition to the new projects, I see a number of luke_mpb files that seem to supersede existing mpbs, such as lukeopenssl.mpb. However I don't see any explicit dependency on this, or any other luke_ files. So how exactly do you use these new mpb files? Best regards, |
I would not be in favor of adding contrib, these luke mpb files can easily be shared by the author in a separate git repository. If there are pure product mpb files that we lack we could add a product mpb that can more easily be used by others and also maintained |
Hi, everybody. I'm sorry for answering so late, I'm a green hand for using github and git. I'm applogize for pushing those mpb file start with luke. It's only template used by my team, and without out source code it can do nothing. the only file to enhance VS2013 is the one vc10.mpt |
when I create VC 2013 project with MPC I found one bug in the script, the mismatch VC version in VC11WorkspaceCreator.pm and VC12WorkspaceCreator.pm will leade to upgrade prompt with MPC generated project. btw vs2015=>14 vs2013=>12 vs2012=>11 vs2010=> ,the former two pm file mistake the vs version match. |
When you can make a separate pull request of the last changes we can quickly integrate those, they don't require testing or something like that. |
how to make a separate pull request? I'm not familiar with github and failed many times to try. @jwillemsen |
See for example http://blog.asquareb.com/blog/2014/06/19/making-a-git-pull-request-for-specific-commits/. You should create a new branch and do a cherry-pick of just that single change and open a new PR |
MPC is a best tool to manage C++ project, the version below 2010 works well, but not works for vc2013, I managed to correct the bug and make all my VC2008 project successfully upgraded to VC2013. I tested type for MFC\DLL\LIB etc.